Improve next.config.js readability and robustness with clearer path resolution and comments#39404
Improve next.config.js readability and robustness with clearer path resolution and comments#39404NirajDN wants to merge 3 commits intogithub:mainfrom
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. This pull request contains code changes, so we will not generate a table of review links. 🤖 This comment is automatically generated. |
|
@NirajDN I have no idea what this does or where it's located, so...let me check into that, and then I'll know who to ask for a review (hopefully🤞). |
|
@Sharra-writes No worries at all ,take your time! If you need the file path or any context, feel free to let me know. 😊 |
|
@NirajDN We don't actually accept changes to this file, because it deals with how we build the site and is under the purview of our engineering team. There's supposed to be a bot that catches these and posts a comment that they can't be changed, but apparently it didn't catch this one. 🤷 Sorry, I'm going to have to close it. |
|
@Sharra-writes No problem at all , totally understand! 😊 |
Why:
Improved
next.config.jsfor better readability, maintainability, and adherence to best practices.fsfrom client bundles.Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
next.config.jsfile.